Re: [PATCH 1/2] Make git blame's date output format configurable, like git log
- From
Jeff King <peff@peff.net>
- Date
- Feb 24, 2009, 05:00 UTC
- Message-ID
- <20090224050028.GB4615@coredump.intra.peff.net>
- In-Reply-To
- <fbb390660902230109k15ed55b7le2ab08bb7dc274b6@mail.gmail.com>
On Mon, Feb 23, 2009 at 01:09:13AM -0800, Eugene Letuchy wrote:
Show 8 quoted lines
> > Maybe this should be a date_format_width() library function? > > I think that's a possible change, but unfortunately my next two > patches would not apply cleanly with a date_format_width change. > > I'm a n00b with respect to git contribution, but is there a procedure > for pushing my blame_date branch remotely so that it's possible to > track a series of patches?
Updating previous work depends on whether it has been picked up in 'next' by Junio; once patches are there, they cannot be rewritten. In that case, you can send a follow-up patch.
In your case, though, the patch is still in 'pu', so you can repost. So I think it makes sense to use "rebase -i" (or the tool of your choice) to make a cleaned up series, and then repost the whole thing as a series.
-Peff