public inbox for archer-commits@sourceware.org
help / color / mirror / Atom feed
From: tromey@sourceware.org
To: archer-commits@sourceware.org
Subject: [SCM]  archer-keiths-explicit-linespecs: reverse-20080717-branchpoint-11886-gfa2e7a3
Date: Wed, 27 Feb 2013 21:05:00 -0000	[thread overview]
Message-ID: <20130227210517.7049.qmail@sourceware.org> (raw)

The branch, archer-keiths-explicit-linespecs has been deleted
       was  fa2e7a386497a7f4ecf5706b5d41838e12f9404b

-----------------------------------------------------------------------
fa2e7a386497a7f4ecf5706b5d41838e12f9404b Initial explicit linespec patch.
-----------------------------------------------------------------------


hooks/post-receive
--
Repository for Project Archer.


             reply	other threads:[~2013-02-27 21:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 21:05 tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-10 19:29 kseitz

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=20130227210517.7049.qmail@sourceware.org \
    --to=tromey@sourceware.org \
    --cc=archer-commits@sourceware.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).