{"thread":{"id":"3344","subject":"[RFC] So... are people happy with commit/status -v?","startedAt":"2006-02-15T09:41:11Z","lastAt":"2006-02-19T15:18:59Z","messageCount":2,"participants":["Junio C Hamano","Christian Biesinger"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"16203","messageId":"7vvevhj6x4.fsf@assigned-by-dhcp.cox.net","threadId":"3344","inReplyTo":null,"subject":"[RFC] So... are people happy with commit/status -v?","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-02-15T09:41:11Z","receivedAt":"2006-02-15T09:41:11Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"I usually never do commits from a subdirectory, also I rarely do\npartial commits, so this is not a big issue to me, but are\npeople happy with the current commit/status?\n\nRegardless of where you started, status is a preview of the next\ncommit with the same set of flags and arguments, so inherently\nthat is a whole-tree operation.\n\nOne thing that _might_ be better, however, is to shorten certain\nparts of the status output when deliberately doing a partial\ncommit.  No matter where you are, \"Updated but not checked in --\nwill commit\" section should stay whole-tree, because it is _the_\npreview of the next commit.  However, \"Changed but not updated\"\nand \"Untracked\" section are different story.\n\nWhen committing from a subdirectory with \"git commit paths...\",\nIt is likely a user forgets about paths that are changed in the\ndirectory and forgets to list them on the command line, so the\nsame directory and below should be listed, but it might not be\nneeded to show files outside the current directory.  \"Untracked\"\nfiles outside the current directory are even less interesting.\n\nEven when committing from a subdirectory with \"git commit\",\nwhich is \"commit the current index contents\", the story is the\nsame.  The user could have forgot to add files in the same\ndirectory or below, but it is less likely that things outside\ncurrent directory need to draw attention to prevent mistakes.\n\"Untracked\" outside are less interesting in this case as well.\n\nIn either partial or whole commit case, however, \"Changed but\nnot updated\" part can be argued important and should be kept\nwhole-tree (myself, I am slightly in favor of keeping this part\nwhole-tree).  After all, the user has changed files in the\ndirectory she happens to be in and outside, and reminding she\nhas something outstanding while previewing the next commit would\nhelp prevent mistakes, whether that modified files are in the\ncurrent directory or outside.\n\nSo, I'm wondering.  I have a feeling that we might be better of\nlimiting \"Untracked\" part to the current directory and below,\nwhile keeping \"Updated -- will commit\" and \"Changed but not\nupdated\" part whole-tree.  OTOH, I do not have strong need\n_myself_ to change the current setup.\n\nComments?  Opinions?\n"},{"id":"16412","messageId":"43F88C63.3020100@web.de","threadId":"3344","inReplyTo":"7vvevhj6x4.fsf@assigned-by-dhcp.cox.net","subject":"Re: [RFC] So... are people happy with commit/status -v?","fromName":"Christian Biesinger","fromEmail":"cbiesinger@web.de","sentAt":"2006-02-19T15:18:59Z","receivedAt":"2006-02-19T15:18:59Z","isPatch":false,"sender":{"key":"cbiesinger@web.de","avatar":null},"body":"Junio C Hamano wrote:\n> I usually never do commits from a subdirectory, also I rarely do\n> partial commits, so this is not a big issue to me, but are\n> people happy with the current commit/status?\n\nThe part that annoyed me most was that \"git-status --only .\" completely \nignores the specified path and tells me about the whole tree, rather \nthan just the current directory and subdirectories. While I think I'd \nprefer it if the commands limited themselves to the current directory by \ndefault, I don't mind the current behaviour, as long as I still have the \npossibility to limit to the subdirectory.\n"}]}