Re: [savannah-help-public] Gnuspeech - git repository

[Marcelo Y. Matuda]

Hi David,

On 09/18/2015 12:55 AM, David Hill wrote:
> Dear Marcelo,
>
> Thanks for writing.
>
> This is a new constraint of which I was unaware. I can only ask
> "Why!". At what level, and what level of detail, would the histories
> be lost? If I split into  the two repos you suggest, why would this
> protect the histories. Also I presume you are talking about the
> histories prior to pushing to the Git repo as an initial load --
> surely the histories *after* the repo is set up on savannah will
> continue to be generated?

The history _after_ the new repository creation will be maintained, of 
course.

But do you remember that you need to remove the .git dir in 
subdirectories? Or else git will create submodules (undesired). In this 
case you delete the _past_ histories, because the history is stored in 
the .git dir.

If you use two repositories, you will not need to delete the .git dir, 
and you will keep the histories.

> If ongoing histories *are* generated, would the loss of earlier Git
> histories matter, as they are mostly covered in the SVN repo and
> really represent cleaning up work? But why would the existing
> histories not be kept (i.e. why would the copies have to be shallow
> copies?). Is that a bug in Git that is documented as a "feature"!
> :-)

If you delete the .git dir, you lose the history and it becomes a 
shallow copy (a copy of only the last versions of each file).

The history in GnuspeechSA is not very interesting, but the Steve's 
GnuSpeech repository is very different from the SVN. The history is 
important to track bugs (what commit created the bug, and who wrote the 
code?).

> If the ongoing histories are *not* generated after the new repo is
> populated, then Git would have a fatal flaw, and I am sure that is
> not so.

This does not happen.

> The earlier histories could be covered in the README, or other
> documentation, if you are just taling about the histories that should
> be in full copies.

> No wonder I get frustrated. This is as bad as Dungeons & Dragons!
>
> I am looking for the simplest, cleanest repo(s) -- preferably just
> one. Submodules cause plenty of their own problems in a shared public
> repository, with several subprojects.

You can have more than one repository, without using submodules.

Imagine a user on GNU/Linux that wants to experiment with GnuspeechSA. 
Why would (s)he be forced to download the OSX code? If you keep a single 
repository, when you clone the repo all files will be downloaded (the 
ObjC code and the C++ code).

> I admit, I am still learning, will investigate further, and am open
> to advice & suggestions.

Somebody (who?) suggested using Github to do experiments (two times, now 
three). When you have a _concrete_ example it is much easier to explain 
things.

Regards,
Marcelo

> Warm regards.
>
> david
>
>
> On Sep 17, 2015, at 18:38 39PM, Marcelo Y. Matuda wrote:
>
> > Hi David,
> >
> > 1- If you use only one git repository: 1a- If you don't use
> > submodules, you will need to do shallow copies and you will lose
> > the histories. 1b- Or you use submodules (undesired). 2- If you use
> > more than one git repository, you will get the complete histories.
> > With the last modifications you need gnuspeech (existing) and
> > gnuspeechsa (new) repositories.
> >
> > Maybe you don't want multiple repositories because Assaf Gordon
> > said: "We can certainly create six sub-repositories under the main
> > gnuspeech, and you could use them as 'git submodules'."
> >
> > See for example http://savannah.gnu.org/git/?group=guix. The
> > project has the repositories: guix.git guix/dhcp.git
> > guix/gnunet.git etc
> >
> > But the repos dhcp.git and gnunet.git are _not_ sub-repositories,
> > they are separate directories. guix.git/ is a directory, and
> > dhcp.git/ is not under guix.git/. I suppose the structure is only
> > to have a better/cleaner directory organization.
> >
> > And if you use multiple repositories, you may or may not use
> > submodules, it is your choice.
> >
> > I know it is confusing, that is why it would be good to do some
> > experiments in a public repository (that you didn't do). Maybe you
> > like adrenaline :)
> >
> > Regards, Marcelo