From: Teemu Likonen <tlikonen@iki.fi>
To: git@vger.kernel.org
Subject: Re: [PATCH/RFC] Make "git remote rm <remote>" remove file refs/remotes/<remote>/HEAD
Date: Sat, 8 Mar 2008 00:18:36 +0200 [thread overview]
Message-ID: <200803080018.36349.tlikonen@iki.fi> (raw)
In-Reply-To: <1204923732-29141-1-git-send-email-tlikonen@iki.fi>
Teemu Likonen kirjoitti:
> If more error checking or something is needed,
Such as finding the .git directory even if $PWD is somewhere else in the
tree.
> I guess
> somebody else has to do it; my skills aren't quite enough. :)
I'm out.
next prev parent reply other threads:[~2008-03-07 22:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 11:38 error: refs/remotes/origin/HEAD points nowhere! Teemu Likonen
2008-03-05 21:24 ` Junio C Hamano
2008-03-06 7:50 ` Teemu Likonen
2008-03-08 22:40 ` [PATCH] builtin remote rm: remove symbolic refs, too Johannes Schindelin
2008-03-09 10:24 ` Junio C Hamano
2008-03-07 21:02 ` [PATCH/RFC] Make "git remote rm <remote>" remove file refs/remotes/<remote>/HEAD Teemu Likonen
2008-03-07 22:18 ` Teemu Likonen [this message]
2008-03-08 1:45 ` Junio C Hamano
2008-03-08 1:46 ` Junio C Hamano
2008-03-08 6:16 ` Teemu Likonen
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=200803080018.36349.tlikonen@iki.fi \
--to=tlikonen@iki.fi \
--cc=git@vger.kernel.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).