Hi,
I recently tried to pull the whole of SVN repository (and it's big)
with git svn. The command I used is:
git svn clone --stdlayout svn_url
The SVN repository itself had trunk/branches/tags layout. But what
happened when I finished the cloning is that master has been set to a
branch (the
(Apologies if this a repeated post. I remember posting once, but it
not to be seen)
On Sep 21, 6:50 pm, Jeffrey jefr...@gmail.com wrote:
For your specific question, I'm not sure there's a way. It's not
[...]
df = diff --no-ext-diff
dfe = diff --ext-diff
Oh yes. Never thought about that.
On Sep 25, 8:15 am, davidshe...@googlemail.com
davidshe...@googlemail.com wrote:
hi,
i found i made a typo error in a commit message which is many commits
away from current HEAD, how can i amend the message? i tried git
commit --commit my commit hash, but it created an new commit and
Hi,
I already have cloned an SVN repository using git-svn. But now a new
directory has appeared in the SVN repo which are outside of the
standard directories - trunk, branch, and tag. To track directory I
manually added the following to my .git/config file:
[svn-remote new_dir]
url =
On Oct 15, 6:23 pm, Marek Wywiał onj...@gmail.com wrote:
[...]
Can You send the output after 'git svn fetch new_dir' command?
I can't figure out what happends.
Unfortunately the command is silent and doesn't give any output,
except the first time I ran it, where, as I said earlier, it threw
2) Suppose I have master branch and topic branch. During my work I am
constantly doing git rebase -i origin/master down to my topic
branch. When I want to merge my Topic branch back to master, should I
do REBASE or MERGE? Why?
Both brings the other branch's changes to yours. Rebasing helps
a plain copy do?
Thanks
Jeenu
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to
git-users+unsubscr...@googlegroups.com.
For more
text files; packing still leaves them as plain text files. Being
binary, I'd think of packing objects for some kind of space/time
benefits. But what's with branch heads here?
Jeenu
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To post
is
this kind of branch naming considered unsafe? Is there a way to make
git accept ref names verbatim, even if there's potential operation
that'd fail because of ambiguity?
Thanks
Jeenu
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To post
On Nov 19, 12:58 pm, Petr Baudis pa...@ucw.cz wrote:
On Wed, Nov 18, 2009 at 08:42:14PM -0800, Jeenu wrote:
On Nov 18, 4:45 pm, Petr Baudis pa...@ucw.cz wrote:
The refs may be packed in .git/packed-refs, if your repository got gc'd
recently - that is nothing to worry about.
Ah
On Nov 19, 4:55 pm, Michael P. Soulier msoul...@digitaltorque.ca
wrote:
On 18/11/09 Jeenu said:
Hi,
If I've two branches a.b.c and a.b.c.d, why does 'git checkout'
complains about ambiguous refnames? For example, if I'm in a.b.c.d,
896 $ git checkout a.b.c
warning: refname 'a.b.c
' command generates the
list of patch files from A. But I can't see how to convert those
patches to a sequence of commits in repo B. I could do a 'git apply
patches/*' but then all patches collapse to one single commit.
Is there any way to achieve what I want? Or are there alternatives?
Thanks
Jeenu
Hi,
I wanted to know the best practice in this scenario:
Let's say I'm working on a branch W. This branches already has changes
merged from two other branches A and B. Now when I work no W, I had to
make changes for bugs/enhancement in the areas of code managed by A
and B. What is the best
-from-the-bottom-up.html
Seconded. The article is one of its kind; describes Git and its
operations from a different perspective.
--
Jeenu
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To post to this group, send email to git-us
for a password.
If everything went fine, you should do
git push origin master
(which tells Git to push local master branch to the remote named
origin) and you're done. You could launch gitk to see that your
branches master and origin/master are at the same commit.
HTH
--
Jeenu
--
You received
and it'll more readable as well. Git will push your commit
graph to the server however it looks.
--
Jeenu
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from
branch topic, you must push topic explicitly. Pushing topic
again wouldn't cause any data transfer as the commit is already
present in remote repo (as it's reachable from master when it was
pushed).
--
Jeenu
--
You received this message because you are subscribed to the Google Groups Git
,
git log master..origin/master --name-status --diff-filter=A
--
Jeenu
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to
git
HTH
--
Jeenu
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to
git-users+unsubscr...@googlegroups.com.
For more options, visit
---E---F---G master
HTH.
--
Jeenu
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to
git-users+unsubscr...@googlegroups.com
it all look complex, but my take is that you
create a dummy repository and play with these commands, especially the
reset. Admittedly, the reset man page has a table listing different
modes, which I personally haven't found very useful.
HTH.
--
Jeenu
--
You received this message because you
content you think is appropriate. In some
cases the resolution is trivial in that you choose content from either
of 3 commits and delete the reset. In other cases it's a mix from all
three.
HTH.
--
Jeenu
--
You received this message because you are subscribed to the Google Groups Git
for human beings
See git help blame for additional options.
HTH.
--
Jeenu
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To view this discussion on the web visit
https://groups.google.com/d/msg/git-users/-/p7K-NYyNUXkJ.
To post to this group, send
On Friday, March 9, 2012 8:44:42 AM UTC+5:30, Jeenu wrote:
Next steps would include a demo as to how SVN would save their day by
helping to recovering from mistakes
Of course I meant Git. What was I thinking?
--
Jeenu
--
You received this message because you are subscribed
-version # This only creates a branch
git checkout your-branch # Move to that branch
--
Jeenu
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To view this discussion on the web visit
https://groups.google.com/d/msg/git-users
25 matches
Mail list logo
