Open GoogleCodeExporter opened 9 years ago
We should probably remove more complex applications from the sfepy repo
completely
and leave only the basic examples used for testing/introducing sfepy to people.
The
applications could be distributed in another repo. The tarball, however, could
still
be used to bundle all.
What do you think?
Original comment by robert.c...@gmail.com
on 17 Dec 2008 at 3:03
+1, I just realized the same thing with hermes an hour ago and right now I am
messing
with "git filter-branch" to filter out my commits into a new repo. We'll think
about
that tomorrow in Pilsen.
Original comment by ondrej.c...@gmail.com
on 17 Dec 2008 at 3:04
Yes, it's stupid having to commit every line commented in an input file which
does
not change the code at all.
In sfepy, I would just remove the files - I do not care they rest in the
history, but
if you have something more clever at hand, then why not.
Original comment by robert.c...@gmail.com
on 17 Dec 2008 at 3:15
I am already using separate git repos for quantum and phono projects, the input
files
in sfepy tend to lag behind. Let us remove them from sfepy - we should leave
there
just the inputs used for the tests - and provide a separate download/git repo
access
for the projects.
Original comment by robert.c...@gmail.com
on 5 Mar 2009 at 10:33
The examples we have now are reasonably small, tested and maintained, so let's
close this.
Original comment by robert.c...@gmail.com
on 3 Dec 2010 at 1:21
Migrated to http://github.com/sfepy/sfepy/issues/60
Original comment by robert.c...@gmail.com
on 30 Jan 2012 at 10:25
Original issue reported on code.google.com by
robert.c...@gmail.com
on 8 Sep 2008 at 7:53