yes that is possible to have scripts create the missing directories.
The reason I asked this is people at my work want to avoid the hassle of having
to create a script for that. They want to checkout seamlessly as they used to
do with subversion.
I guess it is similar as programming in Java and programming in plain old C.
Olivier LE ROY
De : Andrew Keller <and...@kellerfarm.com>
À : Olivier LE ROY <olivier_le_...@yahoo.com>
Cc : "email@example.com" <firstname.lastname@example.org>
Envoyé le : Mardi 8 avril 2014 17h02
Objet : Re: Handling empty directories in Git
On Apr 8, 2014, at 10:47 AM, Olivier LE ROY <olivier_le_...@yahoo.com> wrote:
> I have a project under SVN with contains empty directories.
> I would like to move this project on a Git server, still handling empty
> The solution: put a .gitignore file in each empty directory to have them
> recognized by the Git database cannot work, because some scripts in my
> projects test the actual emptiness of the directories.
> Is there any expert able to tell me: this cannot be done in Git, or this can
> be done by the following trick, or why there is no valuable reason to
> maintain empty directories under version control?
Git is designed to track files. The existence of folders is secondary to the
notion that files have a relative path inside the repository, which is
perceived by the user as folders.
Why can't your scripts create the folders on demand? Or, could your scripts
interpret a missing folder as an empty folder?
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html