From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: git and changelogs
Date: Thu, 17 Jul 2008 22:29:09 +0100 [thread overview]
Message-ID: <49dd78620807171429i19eb7e64x1a8ceb21d16e42fc@mail.gmail.com> (raw)
In-Reply-To: <49dd78620807171424r74f2ddfndf98ef08b6367961@mail.gmail.com>
2008/7/17 Neil Jerram <neiljerram@googlemail.com>:
> 2008/7/16 Ludovic Courtès <ludo@gnu.org>:
>>
>> Speaking of which, your latest commits did not include a ChangeLog
>> entry. :-)
>
> Sorry, yes you're right. I was anticipating the abolition of
> ChangeLogs, but prematurely.
>
> I've added the ChangeLogs in now, but I'm not sure I did the merge and
> push correctly; can you take a look and advise?
>
> What I did was:
> 1. Create 2 new commits in my own repo, with ChangeLogs for the two
> previous commits.
> 2. git pull
> This caused conflicts, because you had an intervening commit that
> modified ChangeLog and libguile/ChangeLog.
> 3. Resolved those conflicts - in terms of the file contents.
> 4. git add ChangeLog libguile/ChangeLog
> 5. git merge
> 6. git push
>
> Was that correct?
(That was on branch_release-1-8. For master I did "git pull" first,
which appears to have avoided some trouble.)
Neil
next prev parent reply other threads:[~2008-07-17 21:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 15:38 git and changelogs Andy Wingo
2008-05-09 20:08 ` Ludovic Courtès
2008-05-17 20:53 ` Han-Wen Nienhuys
2008-05-09 22:41 ` Neil Jerram
2008-05-11 3:09 ` Ludovic Courtès
2008-05-12 19:10 ` Andy Wingo
2008-05-12 20:12 ` Neil Jerram
2008-05-12 21:35 ` Andy Wingo
2008-05-22 21:02 ` Thien-Thi Nguyen
2008-07-11 22:22 ` Neil Jerram
2008-07-15 18:08 ` Ludovic Courtès
2008-07-15 18:28 ` Neil Jerram
2008-07-15 18:54 ` Ludovic Courtès
2008-07-16 21:51 ` Ludovic Courtès
2008-07-17 21:24 ` Neil Jerram
2008-07-17 21:29 ` Neil Jerram [this message]
2008-07-18 13:05 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49dd78620807171429i19eb7e64x1a8ceb21d16e42fc@mail.gmail.com \
--to=neiljerram@googlemail.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).