From: Junio C Hamano <gitster@pobox.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: "Jakub Narebski" <jnareb@gmail.com>, "Git List" <git@vger.kernel.org>
Subject: Re: [RFC PATCH 1/2] add a --delete option to git push
Date: Fri, 14 Aug 2009 00:51:17 -0700 [thread overview]
Message-ID: <7v7hx6suiy.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vab22ubr5.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Thu\, 13 Aug 2009 23\:53\:50 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> I do not mean that this new feature is useless nor stupid. Being able to
> say "git push --delete branch1 branch2" matches _a_ mental model (perhaps
> Hg inspired one) _very_ naturally. There are branches on the other side,
> and there is a special operation called 'delete' that you can inflict on
> them.
>
> But it is a different mental model of how git natively does "push".
> ...
> These are both valid models. They just do not mix, so let's avoid
> confusion by not allowing both at the same time.
One more thing. I suspect that adding --delete and nothing else probably
makes things worse than not doing anything.
In a mental model where "push there --delete $branch" is natural, there
are branches on the other side, and when you run 'push' command, you name
the special operation, 'delete', that you would want to inflict on them.
In such a world, there probably are other (perhaps not so special)
operations you can inflict on the branches on the other side as well.
They are probably called something like:
push there --create $branch $commit
push there --update $branch $commit
If you give them only --delete without completing the vocabulary by giving
these operations as well, you would force people to mix "git native" world
model (i.e. there is no "mode" nor "opration"; there is only "list of
instructions, each of which encodes the equivalent of 'mode'") with this
Hg-inspired world model.
next prev parent reply other threads:[~2009-08-14 7:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 5:05 [RFC PATCH 0/2] add a --delete option to git push Sverre Rabbelier
2009-08-14 5:05 ` [RFC PATCH 1/2] " Sverre Rabbelier
2009-08-14 5:05 ` [RFC PATCH 2/2] test that git push --delete deletes the remote ref Sverre Rabbelier
2009-08-14 5:21 ` [RFC PATCH 1/2] add a --delete option to git push Jeff King
2009-08-14 6:24 ` Sverre Rabbelier
2009-08-14 6:33 ` Jeff King
2009-08-14 6:40 ` Sverre Rabbelier
2009-08-14 6:55 ` Jeff King
2009-08-14 6:53 ` Junio C Hamano
2009-08-14 7:00 ` Jeff King
2009-08-14 7:01 ` Jeff King
2009-08-14 7:05 ` Sverre Rabbelier
2009-08-14 7:51 ` Junio C Hamano [this message]
2009-08-15 2:01 ` Junio C Hamano
2009-08-16 2:30 ` Sverre Rabbelier
2009-08-16 9:19 ` Jakub Narebski
2009-08-14 8:50 ` [RFC PATCH 0/2] " Jakub Narebski
[not found] ` <fabb9a1e0908140953w2d3f571cv3e7415817c2758a7@mail.gmail.com>
2009-08-14 20:25 ` Jakub Narebski
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=7v7hx6suiy.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=srabbelier@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox