{"thread":{"id":"55336","subject":"RFC: Additional git-for-each-repo synopsis","startedAt":"2021-03-17T07:04:34Z","lastAt":"2021-03-17T07:04:34Z","messageCount":1,"participants":["Victor Engmark"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"419447","messageId":"d327e1005e0d487c0c9e8e2f7a9ea17ed6036fce.camel@engmark.name","threadId":"55336","inReplyTo":null,"subject":"RFC: Additional git-for-each-repo synopsis","fromName":"Victor Engmark","fromEmail":"victor@engmark.name","sentAt":"2021-03-17T07:03:44Z","receivedAt":"2021-03-17T07:04:34Z","isPatch":false,"sender":{"key":"victor@engmark.name","avatar":"https://avatars.githubusercontent.com/u/168301?v=4"},"body":"Hi all\n\ngit-for-each-repo is similar to a tool I wrote over a decade ago and\nhave been using ever since,\n`fgit` . \nLooking at the git-for-each-repo documentation it seems it's doing\nthings very differently, and I'm wondering if you would be interested\nin an additional synopsis for the same command:\n\ngit for-each-repo -- \n\nFor example, `git for-each-repo fetch -- ~/*/` would fetch in each\ndirectory directly underneath the home directory. If some of the\ndirectories are not repositories it can easily be amended to\n`~/*/.git/..`, which is going to match only actual Git repositories on\nsane systems. This is similar to the command I run every day or so,\n`fgit pull -- ~/*/.git/.. ~/dev/*/.git/..\n\"/run/media/${USER}\"/*/*/.git/..`.\n\nThis means not having to configure anything to use this tool. The\noverhead of dealing with a configuration file is significant,\nespecially for beginners. It also means not having to go through\nseveral steps every time my collection of repositories changes\n(approximately weekly to monthly), and either coming up with some hack\nfor injecting all my repos into that configuration or forever second-\nguessing whether the configuration is up to date. A third advantage is\nthat this would make it possible to use relative paths.\n\nCheers\nVictor\n\n"}]}