From: "Jessie Hernandez" <jessie@jessiehernandez.com>
To: "Bert Wesarg" <bert.wesarg@googlemail.com>
Cc: "Jessie Hernandez" <jessie@jessiehernandez.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Pat Thoyts" <patthoyts@users.sourceforge.net>
Subject: Re: [RFC][Git GUI] Make Commit message field in git GUI re sizable.
Date: Wed, 22 Feb 2017 12:59:34 +0100 [thread overview]
Message-ID: <dfcc54b406d9f46cf358b7ead128bf65.squirrel@mail.jessiehernandez.com> (raw)
In-Reply-To: <CAKPyHN3f0NwMt1aXx6keSrhaiqRqH6s_xQFdKv5rZ+pL7fmXFw@mail.gmail.com>
> HI,
>
> the reason why it is fixed, is because commit messages should be
> wrapped at 76 characters to be used in mails. So it helps you with the
> wrapping.
>
> Bert
Right ok. I understand.
Knowing this I think I might start writing my commit messages differently
then.
Thank you for this.
Regards
-----------------
Jessie Hernandez
>
>
> On Wed, Feb 22, 2017 at 10:27 AM, Jessie Hernandez
> <jessie@jessiehernandez.com> wrote:
>> Hi all,
>>
>> I have been using git for a few years now and really like the software.
>> I have a small annoyance and was wondering if I could get the
>> communities
>> view on this.
>>
>> When using git GUI I find it handy to be able to re-size the "Unstaged
>> Changes" and the "Staged Changed" fields.
>>
>> I would like the same thing for the "Commit Message" field, or to have
>> it
>> re-size with the git GUI window.
>>
>> I can re-size the "Commit Message" vertically when making the "Modified"
>> panel smaller.
>>
>> Does this make sense?
>> I would be happy to get into more detail if that is necessary or if
>> something is not clear.
>>
>> Thank you.
>>
>> -----------------
>> Jessie Hernandez
>>
>>
>
next prev parent reply other threads:[~2017-02-22 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 9:27 [RFC][Git GUI] Make Commit message field in git GUI re sizable Jessie Hernandez
2017-02-22 9:50 ` Bert Wesarg
2017-02-22 11:59 ` Jessie Hernandez [this message]
2017-02-22 17:15 ` Marc Branchaud
2017-02-23 6:46 ` Jessie Hernandez
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dfcc54b406d9f46cf358b7ead128bf65.squirrel@mail.jessiehernandez.com \
--to=jessie@jessiehernandez.com \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.org \
--cc=patthoyts@users.sourceforge.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).