[git-users] Unexpected behaviour while Migrating HG Mercurial to Git repositories.

[Sandeep Maher]

Hi Team,

Sandeep here, we are using HG Mercurial for the some of our live 
project(s), But now as per the management requirement we need to migrate 
the entire structure as it is to Git.

Meanwhile me and my team tried to achieve the same but due to the complex 
structure of the repositories unable to achieve the same.

 

Requirement *:* suppose we are having some past pushes for code (before 
migration) in main and dependent projects in single change set(Main 
repository and its sub repository),

now after migrating to git, we would like to check out(update to) previous 
version/change set which was pushed in HG. 

And now when we tried to check out/update in main projects, logically 
dependent *project(s)/Repos should get check out/Update to the specific 
version*.. 

But unfortunately it is not happening as expected, 

 

It would be a great help and well appreciated , if anyone could help in 
same.

 

Thanks in Advance,

*Sandeep Maher*

*Consultant.* 

-- 
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] does `git commit` modify $GIT_DIR/index?

[Konstantin Khomoutov]

On Sat, 24 Oct 2015 17:29:30 -0700 (PDT)
ozzloy  wrote:

> does `git commit` modify $GIT_DIR/index?
> i just diffed index from before and after a commit and found no
> difference.  i'm guessing this is reliable behavior, but i wanted to
> make sure.  it seems like the idea of index is that it's always ready
> and waiting to be turned into the next commit.  so commits wouldn't
> ever modify it.
> 
> i'm writing a script that depends on this behavior and i want to make
> sure i have the concepts right.

Care to elaborate on why you want to depend on this?
(We should try to rule out a possible case of the "XY problem" here.)

The problem with your current approach is that Git seemingly says
nothing about how the index-as-a-regular-file behaves in which case
so it's free to change even in point releases.  I mean, I'd try to
avoid such dependancy at all costs until absolutely necessary.

BTW recently someone popped on the main Git list asking about the
current state of affairs in speeding up certain Git operations, and
one of the concepts which were discussed along the way was "split
index".  While I don't know the details it might mean making the Git
index hierarchical -- where some parts of its information are kept in
files, say, adjacent to the main one or whatever.

-- 
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] Unexpected behaviour while Migrating HG Mercurial to Git repositories.

[Gergely Polonkai]

Hello,

first things first: if management decides which free tool you have to use,
run as fast as you can.

Git and Hg are not very different, it is usually pretty straightforward to
migrate between the two. What you are facing now is more likely a
deployment process problem, which is not really in the scope of this list
(which is a community forum, not a support channel as you seem to think).

Neither Git nor Hg is a deployment tool, so if you have this type of
problem, I'm afraid you gave us less than enough information to help, but
if I'm correct, your deployment process is based on Git hooks, so you
probably should read about those first.

Best,
Gergely
On 26 Oct 2015 10:26, "Sandeep Maher"  wrote:

> Hi Team,
>
> Sandeep here, we are using HG Mercurial for the some of our live
> project(s), But now as per the management requirement we need to migrate
> the entire structure as it is to Git.
>
> Meanwhile me and my team tried to achieve the same but due to the complex
> structure of the repositories unable to achieve the same.
>
>
>
> Requirement *:* suppose we are having some past pushes for code (before
> migration) in main and dependent projects in single change set(Main
> repository and its sub repository),
>
> now after migrating to git, we would like to check out(update to) previous
> version/change set which was pushed in HG.
>
> And now when we tried to check out/update in main projects, logically
> dependent *project(s)/Repos should get check out/Update to the specific
> version*..
>
> But unfortunately it is not happening as expected,
>
>
>
> It would be a great help and well appreciated , if anyone could help in
> same.
>
>
>
> Thanks in Advance,
>
> *Sandeep Maher*
>
> *Consultant.*
>
> --
> 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.
>

-- 
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.