From: Andreas Ericsson <ae@op5.se>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Documentation: update description of shell aliases
Date: Thu, 02 Jul 2009 09:21:31 +0200 [thread overview]
Message-ID: <4A4C5FFB.90302@op5.se> (raw)
In-Reply-To: <2e24e5b90907011757r498b8c52v4cf5dfb7016bf8b5@mail.gmail.com>
Sitaram Chamarty wrote:
> On Wed, Jul 1, 2009 at 11:51 PM, Junio C Hamano<gitster@pobox.com> wrote:
>> Sitaram Chamarty <sitaramc@gmail.com> writes:
>>
>>> Aliases that invoke shell commands start from the top-level directory,
>>> but this was not documented.
>> Could you please also think if it is worth mentioning what happens when
>> you do not even have a top-level directory? I.e. in a bare repository.
>
> Yes I thought about it. I decided not to add that because
> it is:
>
> - not common enough (how many new users fiddle in bare
> repos?)
>
I do that quite a lot, but I can't recall ever using an alias
in a bare repo. It would be odd if I did, as the only alias I've
got is this:
alias.wsfix=!git diff HEAD >P.diff && git reset --hard HEAD && git apply --whitespace=fix P.diff && rm -f P.diff
which isn't always doing the right thing even in a non-bare
repository, and never in a bare one.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
prev parent reply other threads:[~2009-07-02 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 16:00 [PATCH] Documentation: update description of shell aliases Sitaram Chamarty
2009-07-01 18:21 ` Junio C Hamano
2009-07-02 0:57 ` Sitaram Chamarty
2009-07-02 7:21 ` Andreas Ericsson [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=4A4C5FFB.90302@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sitaramc@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.