Dear Assaf,
Perfect! Many thanks.
david
On Sep 18, 2015, at 21:14 30PM, Assaf Gordon wrote:
> Hello David and all,
>
> You now have two git repositories:
>
> Anonymous git access:
> git clone git://git.sv.gnu.org/gnuspeech.git
> git clone git://git.sv.gnu.org/gnuspeech/gnuspeechsa.git
>
>
Hello David and all,
You now have two git repositories:
Anonymous git access:
git clone git://git.sv.gnu.org/gnuspeech.git
git clone git://git.sv.gnu.org/gnuspeech/gnuspeechsa.git
Web Access (will take about 30 minutes to update):
http://git.sv.gnu.org/cgit/gnuspeech.git
http://git.sv.g
Dear Assaf,
Probably my lack of detailed knowledge of the structure of the savannah site
threw me. It was the example you gave that caused me some worry the second time
I read it.
git://git.sv.gnu.org/gnuspeech/monet.git
since Monet comes somewhere under gnuspeech.git
I suspect my concern wa
Dear Assaf,
Many thanks. My primary helpers agree on the two repo solution
The name should be gnuspeechsa.git
The two repo solution does solve all the major problems.
Warm regards.
david
On Sep 18, 2015, at 18:57 44PM, Assaf Gordon wrote:
> Hello David and all,
>
> On 09/18/2015 09:07 PM, D
Hi,
On 09/18/2015 09:43 PM, Steve Nygard wrote:
On 2015-09-18, at 16:37, Steve Nygard wrote:
Given those constraints, submodules are the best solution. We can
add GnuspeechSA as a submodule of my repository. Marcelo can
continue his work in his repository, and you can have both projects
to
Hello David and all,
On 09/18/2015 09:07 PM, David Hill wrote:
[Please, savannah hackers, bear with us. Can we have two *separate* Git repos
in the Gnuspeech project:
https://savannah.gnu.org/projects/gnuspeech
The main repository is
git://git.sv.gnu.org/gnuspeech.git
and
http://git.savan
Dear Steve,
You email arrived just as I hit the "Send" button on my last response.
OK. Back to square 2.
So two separate repos perhaps, but read my last response, sent jsut as your
latest arrived!
Nice to think I was close to right after all, based on my previous reading up
on submodules. My
Dear Steve,
You make a powerful, multithreaded case for submodules. You did see what Assaf
said, did you?
"Starting a fresh repository is not a bad idea. Instead of adding the previous
history to a git-commit message, I'd simply create a 'ChangeLog-OLD' file,
listing the detailed changes. For
> On 2015-09-18, at 16:37, Steve Nygard wrote:
>
> Given those constraints, submodules are the best solution. We can add
> GnuspeechSA as a submodule of my repository. Marcelo can continue his work
> in his repository, and you can have both projects together. I'll have to
> read up a bit o
> On 2015-09-18, at 14:16, David Hill wrote:
>
> You will have just seen a copy of my response to Marcelo. If, in fact, the
> full history from Steve's work on Monet is worth keeping in full for git log
> access, instead of putting it in a text file, I could add it to the initial
> commit mes
Hello David,
On 09/18/2015 04:16 PM, David Hill wrote:
The "guix" example I wrote about - is case #2. The related guix
repositories (eg. guix/dhcp.git) are related just by being under
the "guix" directory. Users can pick-and-choose which repository
they are interested in.
Are you suggesting th
Dear Assaf,
Thanks again for your detailed, helpful comments. Much appreciated.
You will have just seen a copy of my response to Marcelo. If, in fact, the full
history from Steve's work on Monet is worth keeping in full for git log access,
instead of putting it in a text file, I could add it to
Hello David and all,
Few comments, hopefully helpful:
Regarding "histories":
The histories in this context is the commit logs of the existing project,
i.e. the date, author, and diff to the source code files.
You can see the current history (of the SVN repo) by doing:
svn co svn://svn.sv.gn
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
As it stands right now, you only need two repositories on savannah:
1. A clone of https://github.com/mymatuda/GnuspeechSA.git
2. A clone of https://github.com/nygard/GnuSpeech.git
That seems pretty simple to me. I think you're making it more difficult than
it needs to be.
I know you're pretty n
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
16 matches
Mail list logo
