From: Junio C Hamano <gitster@pobox.com>
To: David Kastrup <dak@gnu.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Make git-archimport log entries more consistent
Date: Thu, 30 Aug 2007 14:46:49 -0700 [thread overview]
Message-ID: <7v3ay08zli.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <86myw9jwga.fsf@lola.quinscape.zz> (David Kastrup's message of "Thu, 30 Aug 2007 09:47:01 +0200")
David Kastrup <dak@gnu.org> writes:
> ... but given that the previous format was
> not declared canonical at any point of time, the question is whether
> anyone will indeed notice before things break.
I tend to agree with you. archimport is so specialized that if
you are not using it you would not care, and small population
who are using it and relying on the old behaviour would notice
breakaage right away, so "Let's see who screams" sounds like the
right thing to do.
next prev parent reply other threads:[~2007-08-30 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 1:56 [PATCH] Make git-archimport log entries more consistent Miles Bader
2007-08-30 3:14 ` Junio C Hamano
2007-08-30 3:19 ` Miles Bader
2007-08-30 4:10 ` Junio C Hamano
2007-08-30 7:47 ` David Kastrup
2007-08-30 21:46 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-16 5:01 Miles Bader
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=7v3ay08zli.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
/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).