git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's in git.git (Sep 2008, #01; Sat, 06)

From
BGBoyd Lynn Gerber <gerberb@zenez.com>
Date
Sep 7, 2008, 23:48 UTC
Message-ID
<alpine.LNX.1.10.0809071746260.25543@suse104.zenez.com>
In-Reply-To
<7vljy3jzre.fsf@gitster.siamese.dyndns.org>
On Sun, 7 Sep 2008, Junio C Hamano wrote:
Show 15 quoted lines
> Boyd Lynn Gerber <gerberb@zenez.com> writes:
>> On Sun, 7 Sep 2008, Junio C Hamano wrote:
>> ...
>>> I think we already have 6ffaecc (shell: do not play duplicated definition
>>> games to shrink the executable, 2008-08-19), which was cherry-picked from
>>> 4cfc24a (shell: do not play duplicated definition games to shrink the
>>> executable, 2008-08-19) on 'master'.  Do you still have problem building
>>> 'maint' on your boxes?
>>
>> No, maint does build.  I just thought your were going to release
>> 1.6.0.2 from master.  I think the next commit for set-linebug-setvbug
>> needs to be in it for release.
>
> Thanks for clarifying, so as far as you are concerned, 'maint', which is
> the only thing that matters for 1.6.0.2, is in a good shape ;-)

Yes, I guess I miss-understood your maintainer notes. I re-read them before posting. I thought I read that you branch off master for the point releases. I guess that master would be only for 1.6.1 not 1.6.0.2. Sorry for my miss-understanding.

Thanks,

-- Boyd Gerber <gerberb@zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047

Previous: Junio C Hamano
Message 8 of 8 in “What's in git.git (Sep 2008, #01; Sat, 06)”
  1. Junio C HamanoSep 7, 2008
  2. Boyd Lynn GerberSep 7, 2008
  3. Junio C HamanoSep 7, 2008
  4. Boyd Lynn GerberSep 7, 2008
  5. Junio C HamanoSep 7, 2008
  6. Boyd Lynn GerberSep 7, 2008
  7. Junio C HamanoSep 7, 2008
  8. Boyd Lynn GerberSep 7, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.