From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] how to avoid adding labels based on source names
Date: Sun, 03 Jun 2007 12:20:47 -0700 [thread overview]
Message-ID: <1180898390-sup-7346@south> (raw)
In-Reply-To: <20070603181402.GA8650@mona.jeffcovey.net>
Excerpts from jeff covey's message of Sun Jun 03 11:14:02 -0700 2007:
> is there any news on this? there's no rush, but it is the one thing
> that's keeping me from trying sup. :)
I have a patch for it. Going to do a little more testing and then I'll
commit, probably later today.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-06-03 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-27 19:50 jeff covey
2007-05-28 4:12 ` William Morgan
2007-06-03 18:14 ` jeff covey
2007-06-03 19:20 ` William Morgan [this message]
2007-06-04 1:11 ` [sup-talk] gracefully handling missing sources jeff covey
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=1180898390-sup-7346@south \
--to=wmorgan-sup@masanjin.net \
/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