From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: message-position-on-field, push-mark
Date: Thu, 26 Jan 2012 16:43:04 -0600 [thread overview]
Message-ID: <87bopq5blz.fsf@lifelogs.com> (raw)
In-Reply-To: <87vcnyffv6.fsf@gnus.org>
On Thu, 26 Jan 2012 20:01:01 +0100 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Yeah, make your own branch, go wild. It's really easy and cheap to
>> manage branches with Git so don't worry about it.
LI> I think the way to proceed is to create a No Gnus branch (for bug
LI> fixes), and then continue development on the trunk. Perhaps.
Works For Me.
Ted
prev parent reply other threads:[~2012-01-26 22:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 15:19 Philipp Haselwarter
2012-01-03 21:01 ` Lars Magne Ingebrigtsen
2012-01-07 1:57 ` Ted Zlatanov
2012-01-07 6:20 ` Lars Magne Ingebrigtsen
2012-01-07 13:07 ` Ted Zlatanov
2012-01-26 19:01 ` Lars Ingebrigtsen
2012-01-26 22:43 ` Ted Zlatanov [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=87bopq5blz.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).