From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Cc: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] daily kan-ban update 03jun2020
Date: Wed, 3 Jun 2020 17:09:16 -0700
Message-ID: <A4AF384A-E5CA-413E-87FC-338016E6F5E7@getmailspring.com> (raw)
In-Reply-To: <CAPweEDxcPG=+BKLJup+dPH4akmnVAK=NyqoA8H_YfFbMD-rC6Q@mail.gmail.com>
On Jun 3 2020, at 5:03 pm, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> cool. remember also to include the comments - don't delete them. the
> VHDL comments ( "--" VHDL translated to "#" python) are just as
> important to do line-by-line. you'll need to go over the microwatt
> execute1.vhdl and the bugreport because i noticed you deleted some of
> the python docstrings containing the VHDL, without translating the
> VHDL comment strings.
>
> l.
Yes sorry about that, part was intentional, which I see now was clearly
a silly thing to do, the other part was that I managed to really mess up
the 'resolution' of merge conflicts. I was following the same guide I've
used previously (successfully) for git mergetool vimdiff, and for some
reason my attempt to accept the remote changes in favour of my own did
the opposite... and then some, like deleting a bunch of lines near the
top of the file that I did't touch. This all would not have been a
problem had I done a second review of the changes before pushing them
like I was supposed to. Lesson learned.
Cole
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 12:50 Luke Kenneth Casson Leighton
2020-06-03 13:28 ` Tobias Platen
2020-06-03 23:58 ` Cole Poirier
2020-06-04 0:03 ` Luke Kenneth Casson Leighton
2020-06-04 0:09 ` Cole Poirier [this message]
2020-06-04 0:32 ` Luke Kenneth Casson Leighton
2020-06-04 3:46 ` Cole Poirier
2020-06-04 11:02 ` Luke Kenneth Casson Leighton
2020-06-04 22:24 ` Cole Poirier
2020-06-04 0:58 ` Jacob Lifshay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A4AF384A-E5CA-413E-87FC-338016E6F5E7@getmailspring.com \
--to=colepoirier@gmail.com \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git