From: Johannes Sixt <j.sixt@eudaptics.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.3-rc7
Date: Wed, 29 Aug 2007 17:42:58 +0200 [thread overview]
Message-ID: <46D59402.2060807@eudaptics.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708291621120.28586@racer.site>
Johannes Schindelin schrieb:
> To refresh my memory, could you please describe how mingw.git's master and
> devel branches are handled?
'master' merges git.git's tagged releases, i.e. the 'maint' branch, but
also the -rc series of a new feature release (like in the past weeks).
'devel' contains additional commits that make a "flawless" test suite,
i.e. mostly disables tests that trigger bugs. This branch is always
rebased onto of 'master'.
Originally 'devel' contained code changes without which MinGW git would
have been unusable, but currently it really only disables tests that
trigger exotic bugs[*] that I cannot fix right away and so is basically
just for my own convenience. I could very well get rid of the branch -
if only to raise the incentive for others to help fix the bugs. ;)
[*] bugs that I do not encounter in may daily workflow.
-- Hannes
next prev parent reply other threads:[~2007-08-29 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 10:18 [ANNOUNCE] GIT 1.5.3-rc7 Junio C Hamano
2007-08-29 14:12 ` Johannes Sixt
2007-08-29 14:16 ` Johannes Schindelin
2007-08-29 15:08 ` Johannes Sixt
2007-08-29 15:23 ` Johannes Schindelin
2007-08-29 15:42 ` Johannes Sixt [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-29 10:14 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=46D59402.2060807@eudaptics.com \
--to=j.sixt@eudaptics.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.com \
/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 NNTP newsgroup(s).