From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Version tags for customizable variables
Date: Mon, 03 Jan 2011 23:31:18 +0100 [thread overview]
Message-ID: <87pqsdoc09.fsf@dod.no> (raw)
In-Reply-To: <87vd25hbfu.fsf_-_@marauder.physik.uni-ulm.de>
>>>>> Reiner Steib <reinersteib+gmane@imap.cc>:
> When the default value of a variable is changed (or a new customizable
> variable is added) there should be a tag like ...
I wasn't offering up a diff. I was just digging up the change that had
changed the old behaviour.
next prev parent reply other threads:[~2011-01-03 22:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 14:51 Current git HEAD nnimap doesn't do cram-md5 auth Steinar Bang
2011-01-01 15:14 ` Andreas Schwab
2011-01-01 16:47 ` Steinar Bang
2011-01-02 4:42 ` Lars Magne Ingebrigtsen
2011-01-01 17:01 ` Steinar Bang
2011-01-01 17:10 ` Line-wrap on by default: how do I turn it off? (Was: Current git HEAD nnimap doesn't do cram-md5 auth) Steinar Bang
2011-01-01 20:19 ` Andreas Schwab
2011-01-01 21:46 ` Line-wrap on by default: how do I turn it off? Steinar Bang
2011-01-01 21:52 ` Steinar Bang
2011-01-03 7:23 ` Reiner Steib
2011-01-03 8:05 ` Steinar Bang
2011-01-03 22:25 ` Version tags for customizable variables (was: Line-wrap on by default: how do I turn it off?) Reiner Steib
2011-01-03 22:31 ` Steinar Bang [this message]
2011-01-04 7:34 ` Version tags for customizable variables Reiner Steib
2011-01-04 0:05 ` Line-wrap on by default: how do I turn it off? Lars Magne Ingebrigtsen
2011-01-02 4:47 ` Current git HEAD nnimap doesn't do cram-md5 auth Lars Magne Ingebrigtsen
2011-01-02 13:20 ` Steinar Bang
2011-01-02 19:35 ` Lars Magne Ingebrigtsen
2011-01-02 21:33 ` Steinar Bang
2011-01-02 21:41 ` Lars Magne Ingebrigtsen
2011-01-19 21:59 ` Ted Zlatanov
2012-09-13 18:48 ` Steinar Bang
2012-09-13 19:51 ` Steinar Bang
2012-09-13 20:04 ` Steinar Bang
2012-09-13 20:28 ` Steinar Bang
2012-12-24 20:46 ` Lars Ingebrigtsen
2012-12-24 23:13 ` Steinar Bang
2012-12-25 11:40 ` Lars Ingebrigtsen
2012-12-29 8:20 ` Steinar Bang
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=87pqsdoc09.fsf@dod.no \
--to=sb@dod.no \
--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).