From: Joel Brobecker <brobecker@adacore.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
David Howells <dhowells@redhat.com>,
Binutils <binutils@sourceware.org>,
Nick Clifton <nickc@redhat.com>
Subject: Re: Can the automatic daily update commits be stopped, take 2
Date: Fri, 29 Jan 2016 11:40:00 -0000 [thread overview]
Message-ID: <20160129114033.GC23479@adacore.com> (raw)
In-Reply-To: <87d1skacrs.fsf@igel.home>
> > It is hard to tell which one is newer without using git source.
>
> git describe would be the right tool if only we had proper annotated
> release tags.
Which release tags do you have in mind, and what do we need to do
to fix them?
--
Joel
next prev parent reply other threads:[~2016-01-29 11:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 11:08 Can the automatic daily update commits be stopped? David Howells
2015-01-06 11:19 ` Fred Cooke
2015-01-06 11:39 ` Joel Brobecker
2015-01-06 13:08 ` Andreas Schwab
2015-01-06 13:28 ` H.J. Lu
2015-01-06 13:39 ` Joel Brobecker
2015-01-06 15:08 ` Andreas Schwab
2015-01-06 15:13 ` Joel Brobecker
2015-01-06 15:44 ` H.J. Lu
2015-01-06 15:54 ` David Howells
2015-01-06 15:57 ` H.J. Lu
2015-01-06 16:03 ` David Howells
2015-01-06 16:05 ` H.J. Lu
2015-01-06 16:14 ` David Howells
2015-01-06 18:19 ` H.J. Lu
2015-01-06 16:14 ` Will Newton
2016-01-28 22:56 ` Can the automatic daily update commits be stopped, take 2 David Howells
2016-01-28 23:01 ` H.J. Lu
2016-01-28 23:15 ` Mike Frysinger
2016-01-29 0:25 ` H.J. Lu
2016-01-29 0:31 ` Matt Rice
2016-01-29 0:54 ` Mike Frysinger
2016-01-29 10:41 ` Andreas Schwab
2016-01-29 11:40 ` Joel Brobecker [this message]
2016-01-29 12:57 ` Andreas Schwab
2016-01-29 13:37 ` Joel Brobecker
2016-01-29 13:42 ` H.J. Lu
2016-01-29 14:01 ` Joel Brobecker
2016-01-29 14:10 ` H.J. Lu
2016-01-29 13:47 ` Andreas Schwab
2016-02-01 11:58 ` David Howells
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=20160129114033.GC23479@adacore.com \
--to=brobecker@adacore.com \
--cc=binutils@sourceware.org \
--cc=dhowells@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=nickc@redhat.com \
--cc=schwab@linux-m68k.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 read-only IMAP folder(s) and NNTP newsgroup(s).