[git-users] Re: Getting Name and commit message of the person who made the previous check-ins

2013-03-21 Thread Thomas Ferris Nicolaisen
The behavior you are roughly describing doesn't sound like anything TortoiseGit would normally do. You could try asking at their mailing list: https://groups.google.com/forum/?fromgroups#!forum/tortoisegit-users Otherwise, try using the command line next time you do this. Then you can easier sh

Re: [git-users] help, why the same commit in one branch

2013-03-21 Thread lei yang
On Thu, Mar 21, 2013 at 1:47 AM, Dale R. Worley wrote: > > From: lei yang > > > > I git clone git:// > > git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git > > > > find v3.7-rc1 has two same commit ,can some one give me a detailed > > explanation ? > > I see that two different commi

Re: [git-users] help, why the same commit in one branch

2013-03-21 Thread Dale R. Worley
> From: lei yang > > The have the same contents. Meaning that the older commit causes significant changes to the files and the newer commit causes no changes to the files. So someone made a second commit that changed nothing but provided a slightly different commit message. Dale Dale Worley -

Re: [git-users] help, why the same commit in one branch

2013-03-21 Thread lei yang
On Thu, Mar 21, 2013 at 9:40 PM, Dale R. Worley wrote: > > From: lei yang > > > > The have the same contents. > > Meaning that the older commit causes significant changes to the files > and the newer commit causes no changes to the files. So someone made > a second commit that changed nothing b

Re: [git-users] Re: question: how to know from a commit id to know it's merged by which commit id

2013-03-21 Thread lei yang
On Wed, Mar 20, 2013 at 7:55 PM, Thomas Ferris Nicolaisen wrote: > On Wednesday, March 20, 2013 11:34:50 AM UTC+1, lei yang wrote: > >> Hi experts >> >> I think I should have asked this question, but I can't find it know the >> question is >> >> I have a commit id A in tree, how could I know this

Re: [git-users] help, why the same commit in one branch

2013-03-21 Thread Dale R. Worley
> From: lei yang > > I git show , it does change code, and the same as the > first That is quite odd. Have you checked what the graph of commit parents is? Dale -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from thi

[git-users] Do commits remember branch names?

2013-03-21 Thread Brian Jones
In out of the box git, do commits remember the name of the branch that created them? If so, what command can I use to see that information? My assumption is that commits do not record branch names but I want confirmation. Brian -- You received this message because you are subscribed to the Go

Re: [git-users] Do commits remember branch names?

2013-03-21 Thread Konstantin Khomoutov
On Thu, Mar 21, 2013 at 12:48:59PM -0700, Brian Jones wrote: > In out of the box git, do commits remember the name of the branch that > created them? If so, what command can I use to see that information? My > assumption is that commits do not record branch names but I want > confirmation. The

Re: [git-users] Do commits remember branch names?

2013-03-21 Thread Dale R. Worley
> From: Brian Jones > > In out of the box git, do commits remember the name of the branch that > created them? If so, what command can I use to see that information? My > assumption is that commits do not record branch names but I want > confirmation. You are correct, commits do not remember

[git-users] Re: Do commits remember branch names?

2013-03-21 Thread Johan 't Hart
On Thursday, March 21, 2013 8:48:59 PM UTC+1, Brian Jones wrote: > > In out of the box git, do commits remember the name of the branch that > created them? If so, what command can I use to see that information? My > assumption is that commits do not record branch names but I want > confirmatio

[git-users] Re: How to prevent git repo to get big file history back

2013-03-21 Thread Johan 't Hart
On Wednesday, March 20, 2013 7:34:18 PM UTC+1, Ashutosh Kumar wrote: > > Hi, > > I am working on removing big file from my git repo and its history as > well. But i am facing one issue .. > > here is my scenario > > 1. Create a repo > 2. Commit and push a big file > 3. Clone the repo in to test_

[git-users] Re: How to prevent git repo to get big file history back

2013-03-21 Thread Johan 't Hart
Another way you might have a chance of getting rid of the big file: - Do a filter-branch (to get rid of big file) - Create a helper branch - Reset it to the place where the big file was first committed (I mean, not before that commit, but right on it) - Now create a dummy empty file with the same