From: Jon Seymour <jon.seymour@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: 7fb9de4a830dd8969bc17a219c509a76dd3c9aad
Date: Tue, 7 Jun 2005 02:05:23 +1000 [thread overview]
Message-ID: <2cfc4032050606090514981174@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0506060858140.1876@ppc970.osdl.org>
On 6/7/05, Linus Torvalds <torvalds@osdl.org> wrote:
>
>
> On Mon, 6 Jun 2005 jon@blackcubes.dyndns.org wrote:
> >
> > [PATCH] Modify git-rev-list to linearise the commit history in merge order.
>
> Much nicer. Will apply after testing, however, not this part:
>
> > @@ -110,6 +145,8 @@ static enum cmit_fmt get_commit_format(c
> > if (!strcmp(arg, "=short"))
> > return CMIT_FMT_SHORT;
> > usage(rev_list_usage);
> > +
> > + return CMIT_FMT_DEFAULT;
> > }
> >
> >
>
> If you're bothered by a compiler warning (that I don't see, wonder why?),
> please mark usage() and die() with "__attribute__ ((__noreturn__))". Make
> it depend on GCC, ie
>
> #ifdef __GCC__
> #define NO_RETURN __attribute__((__noreturn__))
> #else
> #define NO_RETURN
> #endif
>
> and then do
>
> extern void die(const char *, ...) NO_RETURN;
>
> or something like that.
>
> Anyway, that's indepdendent of this patch, but just fyi.
>
> Linus
>
Here's my gcc version string:
gcc (GCC) 3.3.3 20040412 (Red Hat Linux 3.3.3-7)
Shall I resend you the patch with that taken out?
jon.
--
homepage: http://www.zeta.org.au/~jon/
blog: http://orwelliantremors.blogspot.com/
prev parent reply other threads:[~2005-06-09 4:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 15:39 7fb9de4a830dd8969bc17a219c509a76dd3c9aad jon
2005-06-06 15:44 ` 7fb9de4a830dd8969bc17a219c509a76dd3c9aad [ or: the --merge-order patch ] Jon Seymour
2005-06-06 16:01 ` 7fb9de4a830dd8969bc17a219c509a76dd3c9aad Linus Torvalds
2005-06-06 16:05 ` Jon Seymour [this message]
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=2cfc4032050606090514981174@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=jon@blackcubes.dyndns.org \
--cc=torvalds@osdl.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).