public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Sep 2013, #03; Wed, 11)
Date: Thu, 12 Sep 2013 11:14:36 -0700	[thread overview]
Message-ID: <xmqqsix9q54j.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20130912053644.GB1977@sigill.intra.peff.net> (Jeff King's message of "Thu, 12 Sep 2013 01:36:45 -0400")

Jeff King <peff@peff•net> writes:

> This description is slightly inaccurate since the re-roll. I think it is
> now:
>
>   "git config" did not provide a way to set or access numbers larger
>   than a native "int" on the platform; it now provides 64-bit signed
>   integers on all platforms.
>
> Not a big deal, but it may make your life easier if this description
> ends up in the merge commit, and then you later try to write
> ReleaseNotes off of it.

Thanks, this helps very much.

If you are not interested in how a Git maintainer works, you can
stop reading.

Otherwise understanding of Documentation/howto/maintain-git.txt may
be necessary to grok the below.

The way I work these days is:

 - Add a "###" cut mark to Meta/redo-jch.sh so that topics I want to
   have in 'master' comes before it;

 - Proofread the description on these topics in Meta/whats-cooking.txt;

 - Make a copy of RelNotes to a temporary file and have it in my
   Emacs;

 - On 'master', run "Meta/redo-jch.sh -c1 -e", with emacsclient set
   to my EDITOR;

 - Edit the merge log message if necessary (and if I do so,
   whats-cooking needs to be also updated), but do not say "C-x #"
   yet;

 - Copy that final merge log message to that temporary file (it is
   all in the same Emacs, so this is very simple and easy) to add a
   new entry;

 - Go back to the merge log message and say "C-x #", which will go
   back two step in this list, repeatedly processing all the topics.

And then copy the temporary file over to RelNotes.

next prev parent reply	other threads:[~2013-09-12 18:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 23:32 What's cooking in git.git (Sep 2013, #03; Wed, 11) Junio C Hamano
2013-09-12  5:36 ` Jeff King
2013-09-12 18:14   ` Junio C Hamano [this message]
2013-09-12  6:19 ` Johannes Sixt
2013-09-12 15:24   ` Junio C Hamano
2013-09-13  5:30     ` Johannes Sixt
2013-09-13  5:56       ` Junio C Hamano

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=xmqqsix9q54j.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=peff@peff$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox