From: Andreas Ericsson <ae@op5•se>
To: Paolo Bonzini <bonzini@gnu•org>
Cc: Alex Riesen <raa.lkml@gmail•com>,
git@vger•kernel.org, spearce@spearce•org, gitster@pobox•com,
peff@peff•net, johannes.schindelin@gmx•de, srb@cuci•nl
Subject: Re: [PATCH 7/7] make "git fetch" update all fetch repositories
Date: Tue, 29 Apr 2008 10:48:54 +0200 [thread overview]
Message-ID: <4816E0F6.3030302@op5.se> (raw)
In-Reply-To: <4816D505.1000208@gnu.org>
Paolo Bonzini wrote:
>
>>> Man, that's what release notes are for. You are expected to read those.
>>
>> So you actually read the release-notes for every application you have
>> installed?
>
> Not for every one, but I do for some applications. Right now only git
> and autoconf come to mind. Especially searching for the magic words
> "backwards incompatible" -- the more "power user" you are of an
> application, the more you should read the release notes. And in the
> case of git I don't consider myself a power user but I learnt quite a
> few tricks from the release notes.
>
>> Remind me to never employ you. I doubt you'd ever get any
>> work done.
>
> Well, the same should apply to reading mailing lists...
>
>> Failing that, would you get slightly annoyed, or perhaps even quite
>> vexed if you find out that insert-program-used-to-do-some-work-with-here
>> did omething stupid that made you lose some of your work?
>
> Sorry, how does the patch make you lose some of your work (as opposed to
> some of your time, which is possible as is the case for every backwards
> incompatible change)?
>
Because I will lose some of the refs and then have to dig them up in the
reflog.
> 1) what about the reflog?
>
I'm not comfortable with the reflog. I appreciate its usefulness, but I'm
thoroughly unhappy when I'm forced to use it.
> 2) the patch does not touch refs/heads/* unless you are tweaking your
> configuration (and quite heavily so). IMHO that's using enough rope
> that you really ought to know about the reflog and... look for backwards
> incompatible changes in the release notes!
>
No, but it does touch refs/remotes/*/heads
> 3) your complaint was that it gave errors. Alex did talk about losing
> his work, but questions 1 and 2 would apply to him too.
>
> 4) one man's stupidity is another man's... [fill in] In particular, did
> you understand the rationale for this change? Do you have any
> alternative ideas?
>
Yes, I understand the rationale, and I do have an alternative idea, which
is to make it configurable. Now that I think about it, it's probably useful
to have it togglable via command-line switch as well. Something along the
lines of "git fetch --all-remotes", perhaps. I'm not against the idea as
such. I'm against making it the default.
--
Andreas Ericsson andreas.ericsson@op5•se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2008-04-29 8:49 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 7:31 [PATCH resend] make "git push" update origin and mirrors, "git push --mirror" update mirrors Paolo Bonzini
2008-04-26 17:01 ` Shawn O. Pearce
2008-04-26 17:46 ` Junio C Hamano
2008-04-27 4:30 ` Shawn O. Pearce
2008-04-27 4:40 ` Shawn O. Pearce
2008-04-27 5:23 ` Junio C Hamano
2008-04-27 17:34 ` Shawn O. Pearce
2008-04-27 20:13 ` Junio C Hamano
2008-04-27 20:22 ` Paolo Bonzini
2008-04-28 1:26 ` Jeff King
2008-04-28 5:07 ` Paolo Bonzini
2008-04-28 9:09 ` Jeff King
2008-04-28 9:11 ` Jeff King
2008-04-28 9:19 ` Paolo Bonzini
2008-04-28 10:33 ` Johannes Schindelin
2008-04-28 11:24 ` Paolo Bonzini
2008-04-28 11:57 ` Johannes Schindelin
2008-04-28 3:32 ` Shawn O. Pearce
2008-04-28 5:03 ` Paolo Bonzini
2008-04-28 6:08 ` Stephen R. van den Berg
2008-04-28 1:21 ` Jeff King
2008-04-27 9:03 ` Paolo Bonzini
2008-04-27 7:23 ` Paolo Bonzini
2008-04-28 15:32 ` [PATCH 0/7] limit the usage of the default remote "origin" to the minimum Paolo Bonzini
2008-04-28 15:32 ` [PATCH 1/7] add special "matching refs" refspec Paolo Bonzini
2008-04-30 9:23 ` Junio C Hamano
2008-04-30 9:35 ` Paolo Bonzini
2008-04-28 15:32 ` [PATCH 2/7] add push line in git-clone Paolo Bonzini
2008-05-01 6:28 ` Junio C Hamano
2008-05-06 8:37 ` Paolo Bonzini
2008-05-14 15:20 ` Paolo Bonzini
2008-05-14 18:16 ` Junio C Hamano
2008-05-14 19:07 ` Paolo Bonzini
2008-05-14 19:23 ` Junio C Hamano
2008-05-14 19:40 ` Paolo Bonzini
2008-04-28 15:32 ` [PATCH 3/7] Add a --push option to "git-remote add" Paolo Bonzini
2008-04-28 15:32 ` [PATCH 4/7] make "git push" update all push repositories Paolo Bonzini
2008-04-28 15:32 ` [PATCH 5/7] don't rely on zero-argument "git fetch" from within git pull Paolo Bonzini
2008-04-28 15:32 ` [PATCH 6/7] warn on "git pull" without a given branch.<name>.remote value Paolo Bonzini
2008-04-28 15:32 ` [PATCH 7/7] make "git fetch" update all fetch repositories Paolo Bonzini
2008-04-28 18:10 ` Alex Riesen
2008-04-28 18:19 ` Paolo Bonzini
2008-04-28 21:33 ` Alex Riesen
2008-04-29 4:52 ` Paolo Bonzini
2008-04-29 5:38 ` Alex Riesen
2008-04-29 6:05 ` Andreas Ericsson
2008-04-29 6:55 ` Paolo Bonzini
2008-04-29 16:13 ` Johannes Schindelin
2008-04-29 16:40 ` Paolo Bonzini
2008-04-29 20:34 ` Alex Riesen
2008-04-29 6:50 ` Paolo Bonzini
2008-04-29 7:16 ` Andreas Ericsson
2008-04-29 7:57 ` Paolo Bonzini
2008-04-29 8:48 ` Andreas Ericsson [this message]
2008-04-29 9:02 ` Paolo Bonzini
2008-04-29 21:08 ` しらいしななこ
[not found] ` <200804292108.m3TL8moV011790@mi1.bluebottle.com>
2008-04-29 21:21 ` Paolo Bonzini
2008-04-29 22:21 ` Johannes Schindelin
2008-04-29 20:44 ` Alex Riesen
2008-04-29 21:15 ` Paolo Bonzini
2008-04-29 21:33 ` Alex Riesen
2008-04-29 21:41 ` Paolo Bonzini
2008-04-29 21:53 ` Alex Riesen
2008-04-29 22:26 ` Johannes Schindelin
2008-04-29 23:02 ` Jeff King
2008-04-29 23:17 ` Junio C Hamano
2008-04-30 5:28 ` Paolo Bonzini
2008-04-29 21:39 ` Johannes Schindelin
2008-04-29 20:24 ` Alex Riesen
2008-04-29 19:35 ` [PATCH 0/7] limit the usage of the default remote "origin" to the minimum Jeff King
2008-04-29 21:42 ` Alex Riesen
2008-04-29 21:56 ` Junio C Hamano
2008-04-29 23:12 ` Jeff King
2008-04-30 5:24 ` Paolo Bonzini
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=4816E0F6.3030302@op5.se \
--to=ae@op5$(echo .)se \
--cc=bonzini@gnu$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=johannes.schindelin@gmx$(echo .)de \
--cc=peff@peff$(echo .)net \
--cc=raa.lkml@gmail$(echo .)com \
--cc=spearce@spearce$(echo .)org \
--cc=srb@cuci$(echo .)nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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