From: Dmitry Gutov <dgutov@yandex.ru>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [prop: change]
Date: Wed, 28 Oct 2015 14:38:03 +0200 [thread overview]
Message-ID: <5630C1AB.8070707@yandex.ru> (raw)
In-Reply-To: <87twpbfaiv.fsf@mat.ucm.es>
On 10/28/2015 02:22 PM, Uwe Brauer wrote:
>> I think 2 looks a bit better than 4, wastes less space. Hope that's
>> all right with you.
>
> I'd prefer 4, but I leave that to your judgment. One question I also had
> {tabindent(fill68(desc)).
>
> It seems that you don't like it, but I think it could be handy for very
> long lines in the Changelog file?
IMO, it's better to fix any long-line problems in the commit message
before making the commit.
And if you wrap long lines in vc-hg-log output,
a) You risk not seeing these problems, which is problematic for the
commits you made yourself (other members of your team will see them
differently).
b) There's no guarantee that fill68 won't make some text layout worse.
At least I think so; I've never tried it.
prev parent reply other threads:[~2015-10-28 12:38 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 6:48 vc-next-action RCS vs hg: copies the entry of ChangeLog Uwe Brauer
2015-10-15 10:54 ` Dmitry Gutov
2015-10-18 7:02 ` Uwe Brauer
2015-10-18 7:58 ` Dmitry Gutov
2015-10-18 8:25 ` Uwe Brauer
2015-10-18 9:50 ` Dmitry Gutov
2015-10-18 10:22 ` Uwe Brauer
2015-10-18 13:06 ` Uwe Brauer
2015-10-18 20:04 ` Dmitry Gutov
2015-10-19 6:43 ` Uwe Brauer
2015-10-19 6:55 ` Uwe Brauer
2015-10-19 7:07 ` Eli Zaretskii
2015-10-19 7:18 ` Uwe Brauer
2015-10-19 8:14 ` Uwe Brauer
2015-10-19 8:30 ` Eli Zaretskii
2015-10-19 8:38 ` Uwe Brauer
2015-10-19 8:52 ` Dmitry Gutov
2015-10-19 9:13 ` Dmitry Gutov
2015-10-19 9:04 ` Eli Zaretskii
2015-10-19 9:15 ` Uwe Brauer
2015-10-19 9:20 ` Dmitry Gutov
2015-10-19 10:45 ` Uwe Brauer
2015-10-19 10:51 ` Dmitry Gutov
2015-10-19 10:57 ` Uwe Brauer
2015-10-19 11:02 ` Dmitry Gutov
2015-10-19 13:20 ` Uwe Brauer
2015-10-19 23:46 ` Dmitry Gutov
2015-10-20 6:05 ` Uwe Brauer
2015-10-20 8:34 ` Dmitry Gutov
2015-10-26 16:35 ` [Solved] (was: vc-next-action RCS vs hg: copies the entry of ChangeLog) Uwe Brauer
2015-10-27 13:15 ` [Solved] Dmitry Gutov
2015-10-27 14:23 ` [Solved] Uwe Brauer
2015-10-27 15:15 ` [Solved] Dmitry Gutov
2015-10-27 14:30 ` [Solved] Uwe Brauer
2015-10-27 14:49 ` [prop: change] (was: [Solved]) Uwe Brauer
2015-10-27 15:16 ` [prop: change] Dmitry Gutov
2015-10-27 15:56 ` Uwe Brauer
2015-10-27 17:18 ` Uwe Brauer
[not found] ` <562FB38A.7060007@yandex.ru>
[not found] ` <87eggf1lmy.fsf@mat.ucm.es>
[not found] ` <5630ABD8.1000408@yandex.ru>
[not found] ` <87twpbfaiv.fsf@mat.ucm.es>
2015-10-28 12:38 ` Dmitry Gutov [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5630C1AB.8070707@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).