From: Josef 'Jeff' Sipek <jeffpc@josefsipek.net>
To: Per Cederqvist <cederp@opera.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Iulian Udrea <iulian@linux.com>,
Axel Beckert <abe@deuxchevaux.org>
Subject: Re: [PATCH 0/7] guilt patches, including git 1.8 support
Date: Sun, 20 Jan 2013 16:24:25 -0500 [thread overview]
Message-ID: <20130120212425.GA101005@meili.valhalla.31bits.net> (raw)
In-Reply-To: <50FC5F6B.6070103@opera.com>
On Sun, Jan 20, 2013 at 10:19:39PM +0100, Per Cederqvist wrote:
> On 01/16/13 03:26, Jonathan Nieder wrote:
> >Hi Jeff and other guilty parties,
> >
> >I collected all the guilt patches I could find on-list and added one
> >of my own. Completely untested, except for running the regression
> >tests. These are also available via git protocol from
> >
> > git://repo.or.cz/guilt/mob.git mob
> >
> >Thoughts?
>
> Regarding the "Change git branch when patches are applied" feature,
> it has saved me a number of times since I implemented it. I've been
> using it extensively, and have not had any problems with it.
>
> Nevertheless, for backwards compatibility with the currently
> released guilt version I think it should be conditional, and
> disabled per default for one full release cycle. I've implemented
> this. My code is available from git://repo.or.cz/guilt/ceder.git
>
> The following commits are not included in your list:
>
> a194375 Added guilt.reusebranch configuration option.
> 1dd97bd Minor testsuite fix.
> 640caee The tests should not fail if guilt.diffstat is set.
At $WORK, we started doing thorough reviews before committing. I'm kinda
sold on this feature. I agree with the off-by-default config flag.
> I don't want Guilt to fork. Jeff, it would be really great if
> you could set up a public repo again!
Yep. I'm trying to reclaim control of the repo.or.cz guilt repo... I no
longer have access to jsipek@cs.sunysb.edu and I don't remember the
password.
Jeff.
--
NT is to UNIX what a doughnut is to a particle accelerator.
next prev parent reply other threads:[~2013-01-20 21:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 2:26 [PATCH 0/7] guilt patches, including git 1.8 support Jonathan Nieder
2013-01-16 2:27 ` [GUILT] [PATCH 1/7] get rid of "cat: write error: Broken pipe" error message Jonathan Nieder
2013-01-16 2:27 ` [GUILT] [PATCH 2/7] The tests should not fail if log.date or log.decorate are set Jonathan Nieder
2013-01-16 2:28 ` [GUILT] [PATCH 3/7] Testsuite: get rid of "Broken pipe" errors from yes Jonathan Nieder
2013-01-16 2:28 ` [GUILT] [PATCH 4/7] Handle empty patches and patches with only a header Jonathan Nieder
2013-01-16 2:29 ` [GUILT] [PATCH 5/7] Fix fatal "guilt graph" error in sha1sum invocation Jonathan Nieder
2013-01-16 2:30 ` [GUILT] [PATCH 6/7] Change git branch when patches are applied Jonathan Nieder
2013-01-16 2:31 ` [GUILT] [PATCH 7/7] Drop unneeded git version check Jonathan Nieder
2013-01-16 3:26 ` [PATCH 0/7] guilt patches, including git 1.8 support Theodore Ts'o
2013-01-16 15:04 ` Josef 'Jeff' Sipek
2013-01-20 21:19 ` Per Cederqvist
2013-01-20 21:24 ` Josef 'Jeff' Sipek [this message]
2013-01-27 14:38 ` Josef 'Jeff' Sipek
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=20130120212425.GA101005@meili.valhalla.31bits.net \
--to=jeffpc@josefsipek.net \
--cc=abe@deuxchevaux.org \
--cc=cederp@opera.com \
--cc=git@vger.kernel.org \
--cc=iulian@linux.com \
--cc=jrnieder@gmail.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.