Re: [oll-user] Repository organization
Resources for LilyPond and LaTeX users writing (about) music
Status: Alpha
Brought to you by:
u-li-1973
From: Urs L. <ul...@op...> - 2013-04-12 18:54:58
|
Am Freitag, den 12.04.2013, 19:18 +0200 schrieb Janek Warchoł: > > 2013/4/12 Urs Liska <ul...@op...> > So it remains open: > Any ideas how to deal with the situation? > > The simplest solution would be: > - Just remove all files except the ones needed for the new > repo with a > regular commit > - Move all remaining files to the desired new location in the > directory > structure, also with a regular commit. > Absolutely painless process, but of course each repo would > carry the > whole history. > > Second simplest solution: > - Add only the desired files to the new repos > - Keep the existing repo as the only instance of the history. > > I don't like both. > > > What about: use --filter-branch to harvest as much history as > possible, and stop at that (keeping the existing repo as an archive of > the history)? > > It's not a very good solution, but i'm not sure if doing more is worth > the trouble. > > I think only you can judge this, (as i've obviously had fallen behind > with the project): is the history important enough? Were there many > situations where having current history significantly helped you? One > thing comes to my mind: since the early history is quite tangled, it > may not be very helpful anyway in a few weeks/months from now. Probably you're right. Maybe I just lack the freedom of mind to let that history go ... (as one experienced musicologist told me: be careful with your critical remarks. Don't write too many of them, even as the first sketch: Once you have something written down you don't want to drop that anymore ;-) Maybe that's a good compromise. I'll wait a few days (to see if somebody comes up with another idea), and give it a try. Urs > > > best, > > Janek > |