On Mon, Mar 3, 2008 at 7:07 PM, Nicolas Pitre <nico@xxxxxxx> wrote:
[...]
> You still think in terms of "data used to update a branch". There is no
> such direct relation between the fetched data (objects) and the updated
> branch heads. What you do when listing the commits found between
> origin/master@{1} and origin/master@{0} (or simply origin/master wich
> is equivalent to origin/master@{0}) does not necessarily correspond to
> the data you received during the fetch. For example, it is possible
> that half of those commits were already part of another branch in your
> repository, hence the fetch operation won't download them again. Still,
> the origin/master branch now has acquired them all which wasn't the case
> before. To really _see_ the actually received data during a fetch
> requires internal Git knowledge and digging in the pack directory --
> there is no (need for any) UI for that.
Yes, this time it was me using a completely wrong terminology.
What I was looking for is what Sergei suggested.
> > And how about a repository which have reflogs disabled?
>
> Well, just re-enable them. ;-)
>
> Since they're on by default, if you turned them off then you surely know
> what you're doing and why.
Oh well, very true!
Maybe it's again just me which is still not used to git fetch (or my
mental translation of °fetch° in Italian)
but I found easier to "visualize" the commang "git remote update"
which in my setup alway means
"Fetch updates all the remotes in the repository"
Again, thank you for your comments and for your time.
Ciao,
--
Paolo
http://paolo.ciarrocchi.googlepages.com/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
