Re: Jargon and acronyms on this mailing list
От | Robert Haas |
---|---|
Тема | Re: Jargon and acronyms on this mailing list |
Дата | |
Msg-id | CA+TgmoaH=dg7NBmt1kcPzax+M9Tq0VqFr6Qc6TuWBnpXk7YJJw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Jargon and acronyms on this mailing list (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: Jargon and acronyms on this mailing list
Re: Jargon and acronyms on this mailing list |
Список | pgsql-hackers |
On Mon, Sep 9, 2024 at 1:03 PM Andrew Dunstan <andrew@dunslane.net> wrote: > I guess I could try to write code to migrate everything, but it would be > somewhat fragile. And what would we do if we ever decided to migrate > "master" to another name like "main"? I do at least have code ready for > that eventuality, but it would (currently) still keep the visible name > of HEAD. Personally, I think using HEAD to mean master is really confusing. In git, master is a branch name, and HEAD is the tip of some branch, or the random commit you've checked out that isn't even a branch. I know that's not how it worked in CVS, but CVS was a very long time ago. If we rename master to main or devel or something, we'll have to adjust the way we speak again, but that's not a reason to keep using the wrong terminology for the way things are now. -- Robert Haas EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: