Re: [git-users] An unbelievably newby question

[Konstantin Khomoutov]

On Mon, 12 Oct 2015 11:19:21 -0700
Kenoli Oleari  wrote:

> Thanks for these replies.  I will jump in and try them out.
> 
> For all the cheers about GIT, If find it incredibly difficult to use
> (or to even understand)
> 
> I appreciate the support.

I wonder if you have any prior experience with other version control
systems.  Git was my third VCS (after CVS and Subversion; oh, well, I
also used Visual Source Safe and RCS), and the first distributed one,
and I recall that at first I did have great trouble understanding how on
Earth I would just freaking create a repository to begin with!

Now I understand that the centralized model was so entrenched in my
gray matter that I simply fumbled around trying to find any HOWTO or
a blog post which would map my usual Subversion routine -- go to the
server, initialize a repo there, set it up, return back to the client,
check it out -- to that of Git, and there were literally none.  None!
And all that -- given the huge volume of material available online on
Git even back then when I started using it (something like Git 1.5.x).
I was deeply frustrated ;-)

My problem clearly was in applying certain mental patterns entrenched
in me after mastering two centralized VC systems to a system which used
a set of completely different paradigms.

That's why I'm asking.  If you have a centralized VC model controlling
your thinking about version control, -- that's one thing.  We can help
you unlearn that and learn the new ways.

If, conversely, Git is your first VCS that's a wholly different thing.
Then the problem is supposedly the complexity of the set of paradigms
you have to master to fully understand how a DVCS system, and Git,
works.  Once you know that, using Git won't be hard.  In other words,
the oft-cited claim Git UI is hard is mostly a red herring -- for
instance, try making yourself around, say, Mercurial or Fossil, without
reading 2-3 intros or HOWTOs, and you'll see that there's nothing
ingerently "self-evident" about their UIs as well.  As they say,
«the only truly self-evident user interface is the mother's nipple».
Anything else requires understanding the underlying paradigms.

If that's your case, I'd recommend to start with [1] to get the basics
of a DVCS conveyed in the simplest form possible.  Then some more deep
intro material might help.  Depends on your overall skill level in IT.

1. http://tom.preston-werner.com/2009/05/19/the-git-parable.html

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] An unbelievably newby question

[John McKown]

On Mon, Oct 12, 2015 at 1:19 PM, Kenoli Oleari  wrote:

> Thanks for these replies.  I will jump in and try them out.
>
> For all the cheers about GIT, If find it incredibly difficult to use (or
> to even understand)
>

​Well, although git is great for _me_, there are many who find it arcane
and confusing. But, honestly, it took me a while to get the basics down.
And there are _lots_ which real experts, like Konstantin, know which are so
far above my head, I can't even see them [grin/]. I guess it depends on a
persons mind-set. Especially if they have used some other source control
system before (Subversion users really seem to get tied up in knots because
they want to "just check out one file or branch, not everything" which is
just not how git is designed).​



>
> I appreciate the support.
>
> —Kenoli
>
>
-- 

Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.

Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.

He's about as useful as a wax frying pan.

10 to the 12th power microphones = 1 Megaphone

Maranatha! <><
John McKown

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] An unbelievably newby question

[Kenoli Oleari]

Thanks for these replies.  I will jump in and try them out.

For all the cheers about GIT, If find it incredibly difficult to use (or to 
even understand)

I appreciate the support.

—Kenoli



> On Oct 12, 2015, at 10:35 AM, John McKown  
> wrote:
> 
> I sometimes need to do this too. I start with the command:
> 
> git log -- some.file.txt
> 
> In my case, this is the file: bvir.txt (a strange stat file from another 
> system)
> 
> I enter: "git log -- bvir" (no quotes, of course), and get a list like:
> 
> commit b6cf0ddb83381ed3d0e2001d3d28935106bcbc8c
> Author: John Archie McKown  >
> Date:   Wed Oct 7 08:16:42 2015 -0500
> 
> 10/07/2015 08:25:49 VERSION 01
> 
> commit e106f581ff950a9eddf46e0126414e0407fcd5c3
> Author: John Archie McKown  >
> Date:   Tue Oct 6 08:22:35 2015 -0500
> 
> 10/06/2015 08:31:47 VERSION 01
> 
> commit 98767d3ad5acbb5750f5f9283df787a2ab62f9ab
> Author: John Archie McKown  >
> Date:   Mon Oct 5 08:15:58 2015 -0500
> 
> 10/05/2015 08:25:14 VERSION 01
> 
> commit 3264eb3e79d9949dc56dd3cc5133f8d6198f198a
> Author: John Archie McKown  >
> Date:   Sun Oct 4 08:14:26 2015 -0500
> 
> 10/04/2015 08:24:03 VERSION 01
> 
> commit 1ba481ed914aeb5c3d67f89438b4a91571de997d
> Author: John Archie McKown  >
> Date:   Sat Oct 3 08:14:21 2015 -0500
> 
> 10/03/2015 08:24:03 VERSION 01
> 
> commit 70243d937b03c1be93b786885ca9e7e4f0eb8691
> Author: John Archie McKown  >
> Date:   Fri Oct 2 08:19:50 2015 -0500
> 
> 10/02/2015 08:28:10 VERSION 01
> 
> 
> I can look at that for the one that I want, say the second from the bottom as 
> an example, and do
> 
> git show 1ba481ed914aeb5c3d67f89438b4a91571de997d:bvir.txt >some.other.name 
> 
> 
> If I want to see the differences between that particular one, and the one in 
> my working directory:
> 
> git diff 1ba481ed914aeb5c3d67f89438b4a91571de997d  -- bvir.txt
> 
> This compares only bvir.txt (since it is specified after the --) from the 
> commit and the one in the working directory. If you run on Linux, I have a 
> really "interesting"(?) script that I use to load _all_ of the versions of 
> bvir.txt into separate files in my working directory. I can post it here. 
> There is a BASH shell script, which is 13 lines, and an awk program, which is 
> 11 lines. They may cause "real programmers" to shudder. But they work for me.
> 
> On Sun, Oct 11, 2015 at 1:50 PM, Kenoli Oleari  > wrote:
> I've installed GIT, can do all the actions to commit a file but, somehow, 
> cannot figure out how to actually see a previous version of my file.
> 
> I've tried some commands related to history that return things to me that I 
> can't make any sense out of.
> 
> I've bought several books on this, all of which go into great detail about 
> branches and collisions and remotes and more, but nothing about actually 
> looking at a previous version of a file.
> 
> I even went to a workshop at a conference and couldn't understand enough to 
> ask question about seeing a previous file version in a way that the speaker 
> understood what I was talking about.
> 
> Can someone help me with this?  I'm obviously out in the ozone.
> 
> I'm anxious to make use of this tool everyone is raving about.
> 
> Perplexed...
> 
> --Kenoli
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to git-users+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> 
> 
> -- 
> 
> Schrodinger's backup: The condition of any backup is unknown until a restore 
> is attempted.
> 
> Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
> 
> He's about as useful as a wax frying pan.
> 
> 10 to the 12th power microphones = 1 Megaphone
> 
> Maranatha! <><
> John McKown
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Git for human beings" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/git-users/YzOuh87Kjho/unsubscribe 
> .
> To unsubscribe from this group and all its topics, send an email to 
> git-users+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an e

Re: [git-users] An unbelievably newby question

[John McKown]

I sometimes need to do this too. I start with the command:

git log -- some.file.txt

In my case, this is the file: bvir.txt (a strange stat file from another
system)

I enter: "git log -- bvir" (no quotes, of course), and get a list like:

commit b6cf0ddb83381ed3d0e2001d3d28935106bcbc8c
Author: John Archie McKown 
Date:   Wed Oct 7 08:16:42 2015 -0500

10/07/2015 08:25:49 VERSION 01

commit e106f581ff950a9eddf46e0126414e0407fcd5c3
Author: John Archie McKown 
Date:   Tue Oct 6 08:22:35 2015 -0500

10/06/2015 08:31:47 VERSION 01

commit 98767d3ad5acbb5750f5f9283df787a2ab62f9ab
Author: John Archie McKown 
Date:   Mon Oct 5 08:15:58 2015 -0500

10/05/2015 08:25:14 VERSION 01

commit 3264eb3e79d9949dc56dd3cc5133f8d6198f198a
Author: John Archie McKown 
Date:   Sun Oct 4 08:14:26 2015 -0500

10/04/2015 08:24:03 VERSION 01

commit 1ba481ed914aeb5c3d67f89438b4a91571de997d
Author: John Archie McKown 
Date:   Sat Oct 3 08:14:21 2015 -0500

10/03/2015 08:24:03 VERSION 01

commit 70243d937b03c1be93b786885ca9e7e4f0eb8691
Author: John Archie McKown 
Date:   Fri Oct 2 08:19:50 2015 -0500

10/02/2015 08:28:10 VERSION 01


I can look at that for the one that I want, say the second from the bottom
as an example, and do

git show 1ba481ed914aeb5c3d67f89438b4a91571de997d:bvir.txt >some.other.name

If I want to see the differences between that particular one, and the one
in my working directory:

git diff 1ba481ed914aeb5c3d67f89438b4a91571de997d  -- bvir.txt

This compares only bvir.txt (since it is specified after the --) from the
commit and the one in the working directory. If you run on Linux, I have a
really "interesting"(?) script that I use to load _all_ of the versions of
bvir.txt into separate files in my working directory. I can post it here.
There is a BASH shell script, which is 13 lines, and an awk program, which
is 11 lines. They may cause "real programmers" to shudder. But they work
for me.

On Sun, Oct 11, 2015 at 1:50 PM, Kenoli Oleari  wrote:

> I've installed GIT, can do all the actions to commit a file but, somehow,
> cannot figure out how to actually see a previous version of my file.
>
> I've tried some commands related to history that return things to me that
> I can't make any sense out of.
>
> I've bought several books on this, all of which go into great detail about
> branches and collisions and remotes and more, but nothing about actually
> looking at a previous version of a file.
>
> I even went to a workshop at a conference and couldn't understand enough
> to ask question about seeing a previous file version in a way that the
> speaker understood what I was talking about.
>
> Can someone help me with this?  I'm obviously out in the ozone.
>
> I'm anxious to make use of this tool everyone is raving about.
>
> Perplexed...
>
> --Kenoli
>
> --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.

Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.

He's about as useful as a wax frying pan.

10 to the 12th power microphones = 1 Megaphone

Maranatha! <><
John McKown

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[git-users] An unbelievably newby question

[Kenoli Oleari]

I've installed GIT, can do all the actions to commit a file but, somehow, 
cannot figure out how to actually see a previous version of my file.

I've tried some commands related to history that return things to me that I 
can't make any sense out of.

I've bought several books on this, all of which go into great detail about 
branches and collisions and remotes and more, but nothing about actually 
looking at a previous version of a file.

I even went to a workshop at a conference and couldn't understand enough to 
ask question about seeing a previous file version in a way that the speaker 
understood what I was talking about.

Can someone help me with this?  I'm obviously out in the ozone.

I'm anxious to make use of this tool everyone is raving about.

Perplexed...

--Kenoli

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.