From: Petr Baudis <pasky@suse.cz>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Lower priority of Cogito's default exclude patterns
Date: Sat, 21 Jan 2006 03:04:23 +0100 [thread overview]
Message-ID: <20060121020423.GJ28365@pasky.or.cz> (raw)
In-Reply-To: <20060119140728.GA14998@diana.vm.bytemark.co.uk>
Thanks, patch applied and pushed out.
Dear diary, on Thu, Jan 19, 2006 at 03:07:28PM CET, I got a letter
where Karl Hasselström <kha@treskal.com> said that...
> On 2006-01-19 13:42:44 +0100, Petr Baudis wrote:
> > Oh, now I remember - one my major concern is that now Cogito will
> > not work if not make install'd, which is how I actually primarily
> > use it on my machine.
>
> The not-installed case could easily be worked around by users if
> cogito looked at /etc/cogito/exclude and ~/.cogito/exclude as well.
> (Or maybe that should be /etc/git/exclude and ~/.gitexclude, so that
> e.g. stgit can use the same files.) Would you accept a patch that did
> this?
Sorry, this doesn't make sense to me - how would that help? The user can
as well just make install in that case, instead of manually copying out
one file.
if [ -n "${COGITO_SHARE}" ]; then
COGITO_REAL_SHARE="${COGITO_SHARE}"
return
fi
if [ "${0%/*}" != "$0" ]; then
COGITO_REAL_SHARE="${0%/*}/"
return
fi
# I'm not sure if the following normally ever gets triggered.
# I can only do it by `sh cg-status`. --pasky
COGITO_REAL_SHARE="./$_git_relpath/"
should work well, though.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Of the 3 great composers Mozart tells us what it's like to be human,
Beethoven tells us what it's like to be Beethoven and Bach tells us
what it's like to be the universe. -- Douglas Adams
prev parent reply other threads:[~2006-01-21 2:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 22:19 [PATCH] Lower priority of Cogito's default exclude patterns Karl Hasselström
[not found] ` <20060119100712.GA12154@diana.vm.bytemark.co.uk>
2006-01-19 12:42 ` Petr Baudis
2006-01-19 14:07 ` Karl Hasselström
2006-01-21 2:04 ` Petr Baudis [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=20060121020423.GJ28365@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=kha@treskal.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox