git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Add a reference to gitk localbranc remote/branch in gittutorial

From
PCPaolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Date
Aug 26, 2008, 09:44 UTC
Message-ID
<4d8e3fd30808260244i2eb6c36anaa74771a9649445@mail.gmail.com>
In-Reply-To
<4d8e3fd30808260145k56f5d8dcmbbbd6bcaeaa878a6@mail.gmail.com>

On Tue, Aug 26, 2008 at 10:45 AM, Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com> wrote:

Show 8 quoted lines
> On Tue, Aug 26, 2008 at 10:24 AM, Eric Raible <raible@gmail.com> wrote:
>> On Tue, Aug 26, 2008 at 1:16 AM, Paolo Ciarrocchi
>> <paolo.ciarrocchi@gmail.com> wrote:
>>> +If Alice wants to visualize what Bob did since their historie forked
>>
>> s/historie/histories/
>
> Thanks, fixed.
commit 83f4407bb8e8785d7fc62119010d1412e7cd6508
Author: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Date:   Tue Aug 26 10:13:36 2008 +0200
    Gittutorial update.
    Changes to gitturolia according to the discussion on
    the git mailing list
diff --git a/gittutorial.txt.txt b/gittutorial.txt.txt
index 48d1454..279ca46 100644
--- a/gittutorial.txt.txt
+++ b/gittutorial.txt.txt
@@ -321,10 +321,51 @@ pulling, like this:

 ------------------------------------------------
 alice$ git fetch /home/bob/myrepo master
-alice$ git log -p ..FETCH_HEAD
+alice$ git log -p HEAD..FETCH_HEAD
 ------------------------------------------------

 This operation is safe even if Alice has uncommitted local changes.
+Note that HEAD, that means your current state, can be dropped on either
+side of the two-dot range notation.
+This means that Alice can also inspect what Bod did issuing the following
+command:
+
+------------------------------------------------
+alice$ git log -p ..FETCH_HEAD
+------------------------------------------------
+
+Alice can use gitk to compare what both of them did:
+
+------------------------------------------------
+$ gitk HEAD FETCH_HEAD
+------------------------------------------------
+
+This shows both histories leading to Alice's current state (HEAD) and the
+state Alice just fetched from Bob (FETCH_HEAD).
+
+If Alice wants to visualize what Bob did since their histories forked
+she can issue the following command:
+
+------------------------------------------------
+$ gitk HEAD..FETCH_HEAD
+------------------------------------------------
+
+Two commits written with two dots in between means "show
+everything that is reachable from the latter but excluding
+anything that is reachable from the former".
+
+Alice may want to view what both of them did since they forked.
+She can use three-dot form instead of the two-dot form:
+
+------------------------------------------------
+$ gitk HEAD...FETCH_HEAD
+------------------------------------------------
+
+This means "show everything that is reachable from either one, but
+exclude anything that is reachable from both of them".
+
+Please note that these range notation can be used with both gitk
+and "git log".

 After inspecting what Bob did, if there is nothing urgent, Alice may
 decide to continue working without pulling from Bob.  If Bob's history



Ciao,
-- 
Paolo
http://paolo.ciarrocchi.googlepages.com/
Previous: Paolo CiarrocchiNext: Junio C Hamano
Message 10 of 15 in “Add a reference to gitk localbranc remote/branch in gittutorial”
  1. Add a reference to gitk localbranc remote/branch in gittutorialPaolo Ciarrocchi, Aug 25, 2008
  2. Eric RaibleAug 25, 2008
  3. Paolo CiarrocchiAug 25, 2008
  4. Junio C HamanoAug 25, 2008
  5. Paolo CiarrocchiAug 25, 2008
  6. Junio C HamanoAug 26, 2008
  7. Paolo CiarrocchiAug 26, 2008
  8. Eric RaibleAug 26, 2008
  9. Paolo CiarrocchiAug 26, 2008
  10. Paolo CiarrocchiAug 26, 2008
  11. Junio C HamanoAug 26, 2008
  12. Paolo CiarrocchiAug 27, 2008
  13. Junio C HamanoAug 27, 2008
  14. Paolo CiarrocchiAug 28, 2008
  15. Paolo CiarrocchiAug 27, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.